home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group96a.txt
/
000057_icon-group-sender _Wed Feb 28 03:07:55 1996.msg
< prev
next >
Wrap
Internet Message Format
|
1996-09-05
|
1KB
Received: by cheltenham.cs.arizona.edu; Wed, 28 Feb 1996 10:39:15 MST
To: icon-group@cs.arizona.edu
Date: 28 Feb 1996 03:07:55 GMT
From: "David A. Gamey" <dgameynn@reach.com>
Message-Id: <4h0gub$pk4@nntp208.reach.com>
Organization: Reach Networks
Sender: icon-group-request@cs.arizona.edu
References: <41dvur$hvb@horus.infinet.com>, <4gniib$dta@ns2.ryerson.ca>
Subject: Re: Icon as an editing tool
Errors-To: icon-group-errors@cs.arizona.edu
Status: O
aaab@acs.ryerson.ca (Al Aab - CNED/W94) wrote:
>Bruce S. Tobin (btobin@infinet.com) wrote:
>: I'm looking for a better way to automate (or semi-automate) some heavy
>: C++ editing I'm going to have to do soon, making lots of similar changes to
>: lots of different files.
About two years ago, I worked on a project to rewrite about 3/4M lines of
code into C using automated translation software. Because of many
fundamental semantic differences between the two languages the translator
made many unavoidable mistakes.
I used Icon to to pre-process the source language and post-process the
output of the translator among many other tasks. The code applied over
60 "rules". I ended up writing about 3000 lines of Icon including
whitespace and comments. To do the same in C/C++ would probably have
required 12000 to 17000 lines of code.
Hope this helps.